Add owner-authorized manual workflow triggers - #6964

🤖
I’m Larry.

Summary

People can manually start workflows owned by their managed agents without allowing any channel member to run another owner’s automation. Each request identifies the exact signed workflow version it intends to run. Missing or stale versions, disabled workflows, and revoked authority are rejected.

The CLI and Desktop construct these requests through the shared SDK. Separate invocations create separate runs, including within the same second. Retrying the same signed request returns the original committed run ID and response while its authorization and version remain valid.

Related issue

Stacked on the exact-revision foundation (#6960). Replaces the manual-trigger portion of #6721; automatic agent mention waking is a separate sibling, #6965. No separate issue was identified in the earlier scope search.

Behavior and compatibility

• Only the workflow owner, or that managed agent’s immutable human owner, may trigger it. Current community/channel access and the workflow owner’s required channel role still apply; ownership is not a membership bypass.
• The relay verifies the signed version against the stored workflow and rechecks the definition, lifecycle, and owner’s channel authority in the transaction that saves the request and run.
• Execution and approval resumption use the run’s captured signed definition rather than silently switching to a newer version.
• Third-party clients must send both the workflow ID and signed revision ID. Preserve the same signed event for retries; use a new request identity for a distinct invocation. The SDK supplies that identity automatically.
• Retries after revocation, disabling, or version replacement are rejected. Event-ID deduplication protects run creation in this command path; this is not a general exactly-once execution guarantee. No new run-lookup index or schema uniqueness constraint is included.

Testing

At 0f5fded7, Blox validation passed the full database/relay packages, root unit groups, Desktop Rust tests, formatting, and Clippy. The backend CI archive gate ran all 10 manual-trigger/revoked-owner regressions and 11 foundation database tests against a fresh desired-schema database. Coverage includes out-of-order and same-second requests, sequential and concurrent retries, authorization, approval version binding, and revoked-owner disclosure.